When you add programs to the volume header of a disk, there are two sources for those programs. One is the /stand directory of the system and the other is the /stand directory on an IRIX software release CD. The /stand directory on a CD (usually /CDROM/stand after the CD is mounted) contains copies of sash, fx, and ide that are processor-specific.
As superuser, perform this procedure to add programs to a volume header:
# dvhtool /dev/rdsk/dks0d2vh
(See the section "Device Names" in Chapter 1 for information on constructing the device name.)
Command? (read, vd, pt, dp, write, bootfile, or quit): vd (d FILE, a UNIX_FILE FILE, c UNIX_FILE FILE, g FILE UNIX_FILE or l)? l Current contents: File name Length Block # sgilabel 512 2 sash 159232 3
(d FILE, a UNIX_FILE FILE, c UNIX_FILE FILE, g FILE UNIX_FILE or l)? a /stand/sash sash
As another example, to copy sash from a CD to an IP20 or IP22 system (an Indy(TM)), use this command:
(d FILE, a UNIX_FILE FILE, c UNIX_FILE FILE, g FILE UNIX_FILE or l)? a /CDROM/stand/sashARCS sash
CDs contain multiple processor-specific versions of sash; Table 1-3 lists the version of sash for each processor type.
(d FILE, a UNIX_FILE FILE, c UNIX_FILE FILE, g FILE UNIX_FILE or l)? l Current contents: File name Length Block # sgilabel 512 2 sash 159232 3
(d FILE, a UNIX_FILE FILE, c UNIX_FILE FILE, g FILE UNIX_FILE or l)? quit Command? (read, vd, pt, dp, write, bootfile, or quit): write
Command? (read, vd, pt, dp, write, bootfile, or quit): quit